*************************************************** ** NP00645 FILE ** ** DATE = 06/09/97 ** PHONE = 8-444-0017 ** CONTACT = SANDY PETERSON ** C/T = RD0011 ** USER = SANDYPE NODE = RALVM29 ** *************************************************** APARTXT NA02850 = TCP connection HUNG in FIN1 state. STOP_SYMPTOM APARTXT NA02929 = User can't link to remote or local bridge in Lan Network Manager (LNM) when 6611 router has LNM configured and has specified the virtual ring segment number, but has NOT enabled DLSW SNA. This worked in v1r3, but changes to the v1r4 release for BAN broke it. Oops. Made small change to srbconf.c in proto_cfg to fix this. APARTXT NA02673 = If APPN is reconfigured with a net name, cp name or even different tgs, the old topology data in the safe store on the disk, can cause unusual failures, locates can fail, route calulations can fail. APARTXT NA02719 = When issuing fastpath command DLSW debug -conv a message is returned indication that DLS is not running. A phone call to remote users proves that this is not true. APARTXT NA02813 = There is a potential problem with the DLSw design whenever a HALTLS_N OW msg is sent and the conversation table entry is cleared immediately. It is possible that messages for that conversation may be in the pipe comin g from the other direction when the conv table entry is cleared. Once it is cleared, ANY other conversation can then use that entry. If those "e nroute" messages are then received after another conversation has been starte d using the freed up entry, then confusion and horror will abound for that ne w link station! The possibility of hitting this problem was dramatically increased wi th defect 22691, since that fix causes a lot more HALTLS_NOWs to be sent , instead of HALTFRAMEs. To minimize the risk, the algorithm for selecting an available Conver sation Table entry should be changed. Currently, the algorithm selects the first FREE_SLOT entry that it finds. It should be changed to select the first FREE_S LOT entry that has been free for a certain period of time. Thus, if messages w ere "enroute" for the recently cleared conversation, when they arrive, it will be k nown that the conversation is still in FREE_SLOT and not immediately used by so me other conversation. If enroute messages are received AFTER the waiting period for FREE_SL OT usage, then a potential problem still exists, but since the waiting period s hould be around two minutes or so, this potential should be very, very small. This fix should be made for all mainstream and side releases. APARTXT NA02756 = router configuration reports form system manager or from backdoor config -s or config -d do not show the current config if the cusotmer has made changes via the sytem manager config utility and not committed them. APARTXT NA02758 = Customer set the time on the router from the fastpath using the set time command. They sync'ed their network, but the routers started to show variations. They did not shutdown the routers after doing the update. APARTXT NA02814 = Can't remove all remote ports (also called selected networks) from an interface for AppleTalk. The workaround is to reboot the box; this deletes them. APARTXT NA02775 = It has been discovered during code maintenance that there are some places in the code that do a bzero of a conversation table entry when the code wants to "free" the entry. This is incorrect in that it wipes away some history of the entry, plus, creates an incorrect timestamp of the entry. The correct thing to do is just set the state to FREE_SLOT and set the timestamp. APARTXT NA02761 = activation of 99932 changes time zone to central standard time. This has the affect of changing the clock by some number of hours. APARTXT NA02815 = Several new dlstools options have been added to increase DLSw maintainability. The ability to produce a list of all DLSw semaphores and message queues has been added. Also, the ability to show info about a specific conversation has also been added. APARTXT NA02763 = On a Token Ring port configured for IPX and 802.5 SNAP, frames longer than 2247 are corrupted with 2 bytes of bogus data. APARTXT NA02817 = Improved rawstat statistics for kernel socket debug. APARTXT NA02818 = More info has been added to the convsumm output. In order to fit it all, the format of the output has been changed so that more fits into less area. APARTXT NA02773 = pd_ipxd.tables is prunned to 1 meg by mondisk, but some customers have networks that are bigger then that, /etc/sysmon.files needs to be changed to allow pd_ipxd.tables to be up to 2 meg in size. This apar is a dup of NA02605, which did not fix the problem. APARTXT NA02819 = The file dlsfmt needs to be updated to more closely match the trace point that have been added/changed in the code. APARTXT NA02820 = monproc should not be started by default. monproc will be commented out of /etc/sysmon.conf. It will still be shipped and could be start if for some insane reason somebody ever wants to start it on a particular router. APARTXT NA02852 = Provide priority queuing on OSPF sockets so that hello packets are still accepted when the socket is full (either with byte count or mbuf count). This will allow neighbors relationships to be preserved during times of heavy LSA Update activity such as was observed when Fuji Bank brought up the main trunk between their two data centers. APARTXT NA02851 = Created a tool that processes either an unformatted DLSw trace file, or an already generated formatted DLSw trace file and builds a new formatted trace that is easier to read and follow. It uses output from several dlstools commands in order to make the trace more readable. A more readable trace file makes for better problem debugging! This defect will only concern developers supporting DLSw on the 6611. It has no impact to the function of DLSw or the 6611 and is totally hidden from the customer. APARTXT NA02831 = There is a gated_dump caused by segmentation violation at gated if_conf_close procedure during frequent PPP UP/DOWN negotiation. APARTXT NA02854 = The imminent RIP version 2 support by NCP will not support multicast over Ethernet. This change will allow advertisements of subnets to compensate for NCP/3745's deficiencies. APARTXT NA02853 = When conversation table entries are used without being aged, a warning message should be placed in pd_sysmon.trc. APARTXT NA02754 = More "Way-cool stuff to help diagnose Fuji's Capacity Problem": - kernel socket trace for tracing socket overflow - NAP socket status display for diagnosing NAP socket overflow APARTXT NA02930 = remove.devices shows error when cleaning up X.25 devices. APARTXT NA02844 = inventory changes for r4ap level fx64401 APARTXT NA03043 = There is a misleading description of the 0x08000000 DLC Read/Write Flag bit in dlsfmt. It should describe that it is DLC_TSTF on a read and DLC_RAW on a write. Presently, it just states that it is DLC_RAW. This is misleading. APARTXT NA02932 = Bad Q-elements use counts in fmtdata output APARTXT NA02933 = The ARP display on a soure-route bridged network display the routes wrong in that it does not truncate them to the proper length. APARTXT NA02934 = A change was made with defect 22541 to discard NETBIOS broadcast frames when the analyst queue was backed up. That change works great for NETBIOS. It is time to expand that change to include SNA setup frames (ie. CURFRAMEs, TESTFRAMES, etc). The reasoning is the same as before. If the analyst's queue is backed up, it will take a long time before the analyst ever processes the frames, thus making them useless since any link station associated with them will have already timed out. This situation has been seen with Caremark, where 200+ workstations are trying to connect with a host all at the same time. The analyst's queue gets backed up with TESTFRAMEs and such, and all the link stations just time out because the messages are sitting on the analyst's queue for over a minute. Just toss the meaningless frames right at the beginning and let the workstation keep trying until the analyst is less busy. APARTXT NA02935 = With defect 23023, FREE_SLOT Conv Table entries were aged for two minutes before being reused. If no aged entry was found, then the next available free entry was used, regardless of when the entry was freed. A better solution will be to age all free entries three minutes, minimizing the reuse problem even more. Then, if no free entries are found that are of that age, then the oldest free slot entry will be used. But, the entry will only be used if it is at least one minute old. If no entries are at least one minute old, then the search will fail and no new conversations will be started until a free entry is one minute old. APARTXT NA02949 = Since a change has been made to DLSw to let Conv Table entries 'age' before reusing them, the Conv Table will now most likely have free entries dispersed between entries that are in use. Since 'dlstools conv' only shows the entries in use, it would be helpful to see the index number of the entries being shown. This info will be added to the 'dlstools conv' output. NO FUNCTIONAL CHANGE HAS BEEN MADE TO THE DLSw CODE, just a change to dlstools output. APARTXT NA02936 = Since it has been found that messages that are received late can cause complications with reused link stations, everything should be done to reduce the risk of receiving late messages. One thing that this defect will track is the sending of messages over the TCP socket. If the WAN Writer cannot send a message over the TCP socket within a certain period of time, then the WAN Writer should just bring down the socket. This will cause the link stations using the socket to be cleared, thus the risk of sending a late message to the other side is avoided. Currently, the code already exists in kwan.c to bring down the TCP socket if a write cannot complete in time. But, the default wait time is to wait forever, so in effect, kwan will never bring the socket down. The change will be made to the parms file to indicate to kwan to only wait two minutes for a write to complete before bringing it down. This will prevent late messages from being sent to the partner. APARTXT NA02937 = Whenever DLSw tries to start a link station because it has received a RESPFRAME_cs (started by an ICRFRAME_cs), and the link station fails, it should send back a HALTLS_NOW message to the remote side. This message will allow the remote DLSw to clean up its link station that it just started. APARTXT NA02878 = psna drop APARTXT NA02879 = If you attempt to import a configuration that is greater than 64K from either system manager or fastpath, it fails. APARTXT NA02939 = Selected fixes from GateD list (fixes provided by Acee Lindem): 1. Extra allocation due to extra call to if_ifachange(). 2. Invalid handling of rip_multicast_ifap. 3. The build date is not include in gated_dumps. APARTXT NA02940 = When the analyst receives a NETBIOSNR_ex msg from a remote DLSw and the original NAME QUERY is no longer in the NBOSEX database, the analyst does not free the buffer holding the NAME REC data. This scenario can be hit by either multiple NAME RECs being received from multiple partners, or a NAME REC being received late (ie. after six seconds). This problem does not exist for NETBIOSNR_cs messages. Thus, it is an RFC1795 bug only!! It does not exist in release v1r3_p383fx. This problem was found at Shiseido, PMR 5259x 611 760. APARTXT NA02941 = it's miller time STOP_SYMPTOM APARTXT NA02890 = Problem with DLS not aging out reachability database. It appear s that the date was set back without shutdown of the box, but that is just suspicion at this point. End result is that mac addresses will be unreachable if physical network is re-arranged APARTXT NA02892 = Router hangs at c89 during boot-up. The configuration file size is greater than 64k, and the config daemon tries to write this all to scram in one burst but the socket size is set at 64k max. APARTXT NA03075 = TRS database gets out of sync between routers when using topology safestore. APARTXT NA02942 = ptf test failed, due to bug in psna fix. APARTXT NA02943 = When doing 'dlstools msq' to list all DLSw message queues, dlstools queries WAN message queues that are not in existence because the WAN status is CLEAN/CLEAN. Dlstools should check the WAN status before querying the message queue. APARTXT NA02945 = Currently, dlstools does not include the value of the semaphores that DLSw uses. This is an important value that needs to be displayed in order to shoot semaphore problems. APARTXT NA02946 = DLSw code does not properly handle receiving an interrupt while suspended, waiting on a semaphore. When this occurs, the semop() call returns with an error of EINTR. The current code does not recognize this as an interrupt being received and just returns the error. Unfortunately, very few places that call the sem_lock() function check the return code and thus proceed with their processing as if the semaphore has been locked. This can lead to unpredicable results because two processes will be working with a shared resource AT THE SAME TIME. The fix is to recognize when an interrupt has been received while suspended waiting on a semaphore. When this occurs the sem_lock() routine will issue the semop() again and not return to the caller until it actually has the resource locked. APARTXT NA02947 = Internal Enhancements for NP00645 APARTXT NA02920 = statically defined protocol to dlci mappings do not stay in inarp table if inverse arp is off This symptom applies to IPX, Appletalk, Decnet and Vines protocols APARTXT NA02948 = Basically the problem occurs at intermediate router for a BOOTP CLient REQUEST that going out a FR interface on 6611. The old code can mistakenly a BOOTP REPLY from server AND 2210 VL directly attached to this router, BUT it may be not true! While working on checking for BOOTP REPLY, I found other file arp.c for Ethernet and tr_arp.c, there is a place that the checking is not complete also. However, this is different situation. It is almost impossible. The case only happens as following: a BOOTP Request passes thru 2 routers, first one is 6611 and second one can be any vendor router, they are directly connected via a LAN, AND the second router is NOT in 6611 (first router) ARP cache. In this case, 6611 mistakely think BOOTP Requesta s BOOTP REPLY and retrieve MAC address in BOOTP packet and send out to this MAC address instead of sending ARP query of the second router and route BOOTP REquest to 2nd router after receiving ARP reply from this 2nd router. Even though, this is almost impossible, I put the fix in for completeness for r4ap release only! APARTXT NA02921 = Customer was running NP00600 and experienced SDLC connections dropping after going to NP00602 and FX60204. Error log shows SDL8011 and MPQP_XFTO errors. Traces show that error occurs when 13-byte SDLC frames are sent. APARTXT NA02925 = Error log shows appn abend, system under heavy isr load, line utilization high. APPN view -node shows storage ok, appn view -isr shows multiple sessions. appn is actually out of buffer storage APARTXT NA03041 = sometimes shutdown produces the following message /etc/ACTIVE_KERNEL: No such file or directory APARTXT NA02967 = Scram dump was genarated during scram-start process or ipl time when there is no primary ip address found on a wan port. APARTXT NA03076 = See above APARTXT NA02980 = DLS abends when 12K Ethernet frame received. APARTXT NA03077 = The fix for defect 23138 is not enough if BOOTP server sends BOOTP REPLY directly to BOOTP Client. In this case server send BOOTP reply with UDP dest. port = 68. Therefore the check for BOOTP REPLY OPcode is not enough. The complete check in ip_serial.c for Frame relay interface is: IF (UDP Bcast is ON) for this interface) { /* new */ /* The UDP bcast check is for perf. or cover the case */ /* user select unicast and does not turn on UDP bcast */ /* at all! */ IF ( (IT iS UDP packet) .AND. (UDP dest port is BOOTP CLIENT PORT -port 68) .AND. (BOOTP REPLY) { IF (GATEWAY ADDRESS in BOOTP REPLY IS NOT ZERO){ /* New */ /* Server unicast BOOTP REPLY directly to */ /* if giaddr in BOOTP REPLY is zero. */ then processing setting DLCI. } } } APARTXT NA03078 = . Match ADV_LIST_END() invocations with ADV_LIST() in if.c and policy.c 2. Set RTS_RETAIN and RTS_INTERIOR in interface routes. APARTXT NA03039 = Sometimes with really complicated exports combinations you only an erroneous duplicate entry in the EXPORT list. APARTXT NA03040 = In topologies with dual LANs providing equal-cost paths to non-direct network, OSPF does not compute equal-cost multipath routes when the calculating routers is the DR for the dual LANs. APARTXT NA03079 = Install messages should be more clear APARTXT NA03081 = MRNS v1r4 (NP00644) -- When Authentication Type is set to "Simple" for an OSPF area, a null-string Authorization Key on the interface gives an error on other routers of "Authentication Type Mismatch." Local Fix -- Either disable Authentication type for area by selecting "None" or define a non "null-string" Authorization Key. ENDSET COMPID FOR PTF NP00645 = 564801600,140 PRODID FOR PTF NP00645 = 5648016,Multiprotocol Network Program PREREQ FOR NP00645 = NONE ENDSET COREQ FOR NP00645 = NONE ENDSET SUP FOR NP00645 = NONE ENDSET IFREQ FOR NP00645 = NONE ENDSET MEMO TO USERS = +---------------------------------------------------------------+ | | | MEMO FOR NP00645 | | | +---------------------------------------------------------------+ CONTENTS OF THIS MEMO _____________________ o Description of Supersede and Prerequisite PTFs o Installation instructions for NP00645 o Engineering PTFs with contents included in Production PTFs o New Function Contained in PTF NP00642/640 - SMDS IPX, IP - SDLC Switched Dial In - UDP Broadcast Forwarding (IPHelper) - Option set 1116 - NNS support for DLUR EN - BGP-4 - Multiple IP Addresses - IP Filters - Router Access via Bridged EN Port - APPN APING - IPX PACING AND LARGER SAP/RIP TABLES - Bridge Priority Queueing - System Manager Enhancements - Configuration Enhancements SUPERSEDE AND PREREQUISITE PTFS ________________________________ NP00645 is not a supersede PTF. There are no prerequisite PTFs for NP00645. Any user at base V1R4 can apply this ptf. Having PTFs NP00620, NP00623, NP00625, NP00627, NP00629, NP00640, NP00642, NP00644 though not required, will not prevent NP00645 from being appli ed. All the fixes contained in NP00644, NP00642, NP00640, NP00629, NP00627, NP00625, NP00623 and NP00620 are contained in NP00645. Users at any release levels other than V1R4 must migrate to that level (using NP99932 or NP99931) and be committed at that level before applying NP00645. Note: NP99932 is an MES Upgrade to V1R4 at PTF level NP00625. NP99931 is an MES Upgrade to V1R4 base. PTF INSTALL INSTRUCTIONS FOR NP00645 ____________________________________ Potential problems or delays in the installation procedure can be avoided if you perform certain actions first. CLEANING UP THE 6611 TRANSFER DIRECTORY Receiving installation files places them in the transfer directory of the 6611. If you know you have unnecessary files in the transfer directory (such as outdated dumps or reports), delete the files before beginning the installation. Refer to "Delete Transfer Directory Files" in the Operations chapter of the IBM Multiprotocol Network Program Operations and Problem Management manual for details. STOPPING TRACES Before beginning the installation process for any update, stop all trace activities. Active traces might cause installation to fail because of insufficient space. Refer to the Problem Determination chapter of the IBM Multiprotocol Network Program Operations and Problem Management manual for information on stopping traces. In particular, it is important that IP routing (gated) protocol traces should be stopped before installing this PTF. HANDLING DEVELOPMENT PTFS Before beginning the installation process for any software update, check to see if you have any development PTFs on your system. Development PTFs may be identified as containing the characters FX in their names, for example: Name: mpnp.obj NP00001 ---------------------- Fix ID Release ************************* FX00001 01.01.0000.0001 If you know that you have development PTFs on your system, call your IBM Support Center and provide the following information: o The development PTFs that are already on your system o The software updates you wish to install INSTALLING SOFTWARE UPDATES Software updates are installed from the transfer directory using the Software Installation and Maintenance Facility of the Multiprotocol Network Program V1R3 Supplement(SD35-0238). This is a multiphase process that permits the software updates to be tested before making them a permanent part of the Multiprotocol Network Program. When updating software, the first step after importing the software update is to apply the software update. After a software update is applied to a 6611, it can be activated at a later time. You can specify the maintenance level and the date and time of the activation. The 6611 will be re-IPLed at activation time. Thus, the application of a PTF is not directly coupled with the re-IPL of the router. Any software update that is applied, but not activated in the currently running 6611, can be rejected at any time. A software update must be active before it can be committed. Warning: When you commit the software update, the change is permanent. There are several rules to consider when installing software updates that have dependencies: o Software updates cannot be applied until their prerequisite software updates have been applied. o Applied software updates cannot be committed until their prerequisite software updates have been committed. Possible Messages When Applying PTFs: If there is not sufficient space available, you will see a system message similar to: Installation failed. Please press enter to view the detailed information. (Assuming Enter is pressed, this detailed message is displayed:) installp could not complete because there is not enough space in file system /usr. It needs 476 more 1K blocks. The space available in /usr is less than the minimum required for this operation. The selected install operation will not be started now. Press Enter to continue. If there are more than 1000 1K blocks free in each file system, then you will see different messages depending on whether there was sufficient room for the PTFs you selected to apply. NOTE: If you have insufficient space in the file systems other than /tmp and you have commited all prior PTF's, you must contact IBM service. IBM service will make the appropriate adjustments to the file systems. If you select multiple PTFs to be applied and there is room for some, but not all, only the ones that fit will be applied. The log file pd_update.log in the transfer directory will inform you of this. To perform software updates from the System Manager: 1. Log in to the System Manager using a controlling user ID. 2. Select Software Installation and Maintenance on the System Manager main menu. Follow this procedure to install your software update using the System Manager: Step 1 Your software update is sent to you on diskettes or tape. The software update must be moved to the transfer directory for installation. Before proceeding, refer to "Recommended Software Pre-Installation Actions" for suggested actions if you have not already done so. Step 2 Select Receive Software Updates from the Software Installation and Maintenance menu to move the update files to the transfer directory in the 6611. These import methods are available: * FTP * Modem * Tape * Diskette Before receiving any software files, the system validates that enough space is available in the transfer directory. NOTE: Steps 3 and 4 are optional steps for informational purposes only and are not required for this installation Step 3 Select List Software Updates in the Transfer Directory to view a list of the software in the transfer directory of the 6611, Step 4 Select List All Problems Fixed by Software Updates to list the problems fixed by the software updates in the transfer directory. Step 5 Select Apply Software Updates to install the software updates on the 6611. The installation ends without a re-ipl, and you are returned to the Software Installation Maintenance menu. Step 6 Select Activate Applied Software Updates to activate the applied software updates. In the first selection screen, select NP00645. In the second selector screen you must use "none" as a selection if that is the only choice or if you wish to select no EPTF's. COMMITTING THE SOFTWARE UPDATE (PTF NP00645) CAUTION: When you commit the software update, the change is permanent. You will not be able to reverse the commit. When PTF NP00645 is committed, underlying PTFs are committed also. All EPTFs(FX....) are rejected when NP00645 is committed. Step 1 Select Commit Active Software Updates to commit the activated software updates. Refer to Chapter 5 "Software Installation and Maintenance" in the Multiprotocol Network Program Supplement Version 1 Release 3 (SD35-0238) more installation information. ------------------------------------------------------------ Installation of PTF NP00645 along with the prerequisite and corequisite PTF's, will alleviate the need for the engineering PTF's listed below to reside on your machine. NOTE: If you are currently running with an Engineering PTF that is not on the list below, contact your IBM Service representative for possible additional instructions. FX62001 FX62002 FX62301 FX62302 FX62303 FX62501 FX62502 FX64001 FX64201 FX64202 FX64203 FX64401 FX64402 FX64403 The Functional Enhancements described below were available in PTF NP00642/640 unless otherwise noted. All functional enhancements in NP00642/640 are also available in NP00644 which replaced NP00642. NP00645 contains only fixes, but no new function, it replaces NP00644. ----------------------------------------- * NNS support for DLUR EN - Option Set 1116 ----------------------------------------- This feature enables the 6611, when configured as an APPN NN, to understand when a DLUR EN that supports Option Set 1116 registers its LUs. The Dependent LU Requestor (DLUR) architecture has been enhanced to allow DLUR End Nodes to register their LUs with a Network Node Server so that searches do not need to take place each time. This can cut down significantly on unneeded network searches. The 6611 cannot be configured as an End Node but now has the Network Node Server support to receive the LU registration and recognize the LU as a DLUR LU. ----------------------------------------- * BGP-4 ----------------------------------------- Border Gateway Protocol (BGP) uses policies to control the advertisement of routes across organization (autonomous system) boundaries. Thus BGP is used to interface an organization's network with one or more providers of Internet service. BGP is also used by service providers to interface with each other. Note that BGP can also be used to control the distribution of route topology information within a large private network. BGP-4 is described in RFC-1657. The key difference between it and BGP-3 has to do with aggregation of routes. With BGP-3 all advertisements must be for classical network addresses. BGP-4 allows contiguous addresses to be aggregated. Any address prefix can be advertised as long as the advertiser provides routes to all the included addresses. So the hope is that providers will be able to aggregate the network addresses of their users and reduce the large number of routes that must be advertised today for complete information about large networks. BPG-4 also facilitates CIDR (Classless Inter-Domain Routing) since it allows an organization to advertise a block of class C networks with a single advertisement. CIDR was shipped on the 6611 in V1R4. The 6611 implementation of BGP-4 has the following limitations: - It does not support the full Internet routing table (35-40,000 routes). - The BGP-4 MIB is supported as SNMPv1 rather than SNMPv2 as specified in the RFC. ----------------------------------------- * SMDS Integration (IP and IPX) ----------------------------------------- Switched Multimegabit Data Service is a high performance, connection-less, public switched data service designed to interconnect LANs and provides LAN-like features and performance across Wide Area Networks. SMDS uses cell relay switching technology. Generic system requirements are defined in Bellcore specification TR-TSV-000722. RFC-1209 defines the handling of IP and ARP packets and encapsulation, and SMDS complies with IEEE standard 802.6 MAN. The service provides individual, group and ARP addresses at DS1 (1.5Mbps), DS3 (45Mbps) and SONET (155Mbps) speeds. It also supports a slower speed option of 56-64Kbps. The 6611 supports speeds from 56Kbps through DS1. SMDS was initially shipped on the 6611 as a PRPQ (Programming Request for Price Quotation). In PTF NP00640, the code was incorporated into the mainstream 6611 MPNP code and supported IP only. In PTF NP00642, SMDS supports IPX as well as IP. The SMDS WAN protocol can be configured on A25 or A47 two or four port serial adapters or on either LAN/WAN combo adapter. It is not supported on the old serial adapters. **************************************************************** *SUPPLEMENT TO 6611 NETWORK PROCESSOR OPERATION POCKET GUIDE * **************************************************************** **************************************************************** *** If you receive this document in softcopy format and *** *** print it, symbols, for example, in fast path commands, *** *** may not resolve accurately for some printers. Please *** *** refer to the IBM MPNP Operations and Problem Management *** *** Guide, SC31-6691 for a description of how to use these *** *** commands. *** ***************************************************************** This chapter supplements the information in Chapter 4 of the 6611 Network Processor Operation Pocket Guide, GX27-3909. These guidelines describe how fast-path commands are structured: * Brackets ([ ]) surround: - Groups of options separated by an |, when only one option in the group can be specified (for example, [-diskette|-tape]) - Groups of options separated by an &|, when one or more options in the group can be specified (for example, l(-packet) &| -frame]) * Parameters are in double quotation marks (" "). * Parentheses (( )) surround any defaults for the subobjects, actions (depending on the subobject), and options. * Braces ({ }) surround options and parameters that are not required. *************************************************************** SMDS Commands Use the SMDS commands to: * View the SMDS ARP Tables * Delete all entries from the SMDS ARP Tables * Clear SMDS statistical counters * View the SMDS individual address, group address and ARP address associated with a given interface * View the SMDS statistics for a given interface * List interfaces configured for SMDS * View the SMDS MIB Error table for a given interface Object Abbreviations: smds: SMDS, sm Subobject Abbreviations: address: addr, ad arp: a statistics: statistic, stat, s Action Abbreviations: clear: clr, c delete: del, d list: l view: v Option Abbreviations: -active: -act, -a -all -IP -ip -IPX -ipx -miberr: -me Summary of SMDS Commands smds address (view){-log} "interface" - View the SMDS individual address, group address and ARP address associated with a given interface. smds arp delete [(-all)|-IP|-IPX] "interface" - Delete entries from the SMDS ARP Tables. smds arp (view) {-log} [(-IP)|-IPX] "interface" - View the specified SMDS ARP Table. smds list {-active} {-log} "interface" - List the serial interfaces configured for SMDS. smds statistics clear "interface" - Clear SMDS statistical counters. smds statistics (view) {-log} "interface" - View the SMDS statistics for a given interface. smds statistics (view) -miberr {-log} "interface" - View the SMDS MIB Error table for a given interface. ----------------------------------------- * Multiple IP Addresses (MIA) ----------------------------------------- Prior to this function, the 6611 supported only one IP address per physical interface. This function supports multiple IP addresses on single token ring and ethernet ports. The 6611 implementation of MIA has the following limitations: - MIA is only supported on LAN adapters (token ring and ethernet). - A maximum of 10 IP addresses is allowed per physical interface with a total of 66 addresses per router. The network (sub-network) portion of the secondary address of each interface must be unique within the router. - Each IP address may have its own subnet mask. - No subnet overlapping is permitted. This restriction does not apply to the loop-back address (127.0.0.1) or the multicast address (224.0.0.x). ----------------------------------------- * IP Filters ----------------------------------------- This function allows a customer to enable traffic such as telnet and ftp (both requests and responses) to flow in one direction but not in the other. An example would be where a user might want to telnet/ftp out to the Internet but where the customer might want to restrict external access into his/her network. Customers can now choose filtering based on TCP/UDP source port, destination port or both. Prior to NP00640, filtering had to be symmetrical, that is, the restrictions had to be the same in both directions. ----------------------------------------- * Router Access via Bridged EN Port ----------------------------------------- A bridged Ethernet port can be accessed via telnet for the purposes of logging into the box. Prior to this PTF, this function was only available on token ring ports. ----------------------------------------- * SDLC MIB ----------------------------------------- Ther are two new SNMP SDLC traps that provide port and link station (LS) status. Port UP/DOWN status has also been made more accurate. Note that this function was also provided in V1R4 via PTF NP00623 and in V1R3 via PTF NP00387. ----------------------------------------- * APPN APING ----------------------------------------- An "APING" can be issued from a 6611 to any other APPN device supporting APING including another 6611, VTAM or Comm Manager/Server. APING may also be issued from one of these latter devices to a 6611. The target device does not have to be physically adjacent to the originator as long as an APPN "route" is active between the two devices. APING can be issued from a 6611 via the System Manager fastpath or a via a System Manager screen. ----------------------------------------- * IPX Pacing and Larger SAP/RIP Tables ----------------------------------------- IPX has been enhanced to provide SAP and RIP tables with 4096 entries which is twice the size of the tables in V1R4 and prior releases. In addition, IPX SAP and RIP pacing has been added to the PPP interface. ----------------------------------------- * Bridge Priority Queueing ----------------------------------------- This function provides bridge filtering that can be applied to determine the priority of SEND frames as high/medium/low. ----------------------------------------- * Switched SDLC Dial In ----------------------------------------- Allows PU Type 2.0 dial in to a 6611. ----------------------------------------- * UDP Broadcast Forwarding ----------------------------------------- This function (also know as IPHelper) allows configuring a destination address rather than a local port address as the target for forwarded UDP broadcast packets. Thus one can configure the DHCP/BOOTP server address as the target for a DHCP/BOOTP client and not worry about either the path to the server or the increased broadcast traffic on intermediate networks. ----------------------------------------- * System Manager Enhancements ----------------------------------------- The System Manager has been enhanced to provide screen and fastpath commands for APPN network debugging and other functions. Note that APPN fastpath commands were also provided in V1R4 PTF NP00623. ----------------------------------------- * Configuration Tool ----------------------------------------- The 6611 Configuration Tool has been enhanced to support the new functions in PTF NP00644. The current PTF level of the V1R4 Configuration Tool is NP00668. This Tool may also be used to configure all 6611 V1R4 routers. A Configuration UPGRADE is NOT required. The customer is warned if he/she attempts to configure function only available in PTFs NP00640, NP00642 NP00644 or NP00645. I n most cases, if the customer chooses to ignore this warning and configures enhanced function on a V1R4 router without the appropriate Enhanced Function PTF (NP00640-NP00645), the new function will be ignored -- however, this is not guaranteed. Additional information specific to the new Configuration Tool can be found in the README file on the Configuration Tool installation diskettes. END OF MEMO - NP00645 ENDSET LABELTXT Selective Fix Package For use on MPNP V1, R4.0 only ENDSET ***************************************************